programming4us
           
 
 
Windows Server

Windows Small Business Server 2011 : Sharing Printers- Understanding Windows Printing

- Free product key for windows 10
- Free Product Key for Microsoft office 365
- Malwarebytes Premium 3.7.1 Serial Keys (LifeTime) 2019
7/11/2013 7:20:41 PM

In addition to the hardware that actually does the printing, Windows computers have a number of other components devoted to their print architecture. The main components of a shared printer solution in the Windows environment are as follows:

  • Print device In Windows, the term print device refers to the actual hardware that produces the hard copy output from a print job. Windows enables you to share a print device that is connected to any computer on the network using a universal serial bus (USB), IEEE 1394 (FireWire), or other port; or connected directly to the network.

  • Printer Although the term is commonly used to refer to the hardware, the term printer, in Windows, actually refers to the logical representation of a print device that appears in the operating system and on the network. You can create a printer in Windows without there being an actual print device connected to the computer or the network, and it will appear in the Devices And Printers Control panel just as if the hardware were present. A Windows printer tells the system which port, or interface, it must use to connect to the print device, as well as the printer driver the system must use to process its print jobs and communicate with the print device.

  • Print server A print server is the component responsible for holding print jobs in a queue and sending them, one at a time, to the print device. A print server can be a dedicated hardware component that connects the print device to the network, but more often, one (or more) of the computers on the network functions as the print server. In Windows printing, you can create a single print server that receives jobs from all the clients on the network and feeds them to the print device, or each client can function as its own print server, sending jobs directly to the print device.

  • Printer driver The printer driver is the software component that receives output from applications generating print jobs and converts it into a data stream using a page description language (PDL), which consists of commands that the print device understands. Windows printer drivers generate print jobs using an interim format called Enhanced Metafile (EMF). The EMF data is then converted into a device-specific RAW format, either by the client or the print server, depending on the printer configuration. The print server then stores the RAW data in the print queue until the print device is ready to accept it.

Note

Administrators can distribute these components around the network in various ways, to accommodate the printing strategy they want to create. Every computer that generates print jobs must have a printer and a printer driver, but you can locate print servers and print devices anywhere on the network.

Windows Printing Process

The process by which a computer prints a document includes the following steps and is shown in Figure 1:

  1. A user working with an application activates its print function, selects one of the printers installed on the computer, and configures application-related settings, such as what pages of the document to print.

  2. The application calls the printer driver associated with the selected printer, enabling the user to configure printer-related settings, such as which paper tray to use.

  3. The printer driver converts the application’s print output into XML Paper Specification (XPS) or EMF commands and data, which it sends to the print server.

  4. The print server stores the job in a print queue called a spooler, in which it waits until the print device is ready to accept the job.

  5. When the print device is ready, the print server reads the job from the spooler, converts it from EMF to a Printer Control Language (PCL) format, if necessary, and sends it to the print device using the appropriate port.

  6. The print device receives the job from the print server, processes the commands and data, and generates the hard copy output.

The Windows printing process.

Figure 1. The Windows printing process.

Designing a Network Printing Solution

The printing architecture on a small business network is usually not complicated. Small businesses typically have, at most, two or three print devices, but administrators still have to make design decisions such as the following:

  • How will the print devices connect to the network?

  • Which computer(s) should function as print servers?

  • Who has access to the print devices and when?

  • Who is responsible for daily printer maintenance?

Connecting Print Devices

Before you can share a print device with your Windows SBS 2011 network, you must connect the hardware to one of the computers on the network or connect it directly to the network. Most of the print devices on the market today connect to a computer using a USB or IEEE 1394 port, and many also have an integrated network interface adapter, which enables you to connect the device directly to your Ethernet or wireless network. Older print devices might connect to a computer using a parallel or serial port, and, in some cases, you can purchase a network interface adapter as an expansion card that plugs into the printer. Finally, you can purchase an external print server device that connects directly to the network and has a port for connecting the print device.

The type of print device connection you use should depend on your network design, the layout of your office, and, as always, your budget. When you connect a print device to a computer, as shown in Figure 2, that computer functions as a print server, receiving jobs from other computers on the network and feeding them to the print device. Any Windows computer, whether server or workstation, can function as a print server. However, if your users do a lot of printing, the print server functions can impose a significant burden on a workstation that does not have much more than the minimum recommended Windows hardware to support them. A constantly running printer can also be an annoyance to a user trying to accomplish other tasks on the workstation.

A print device connected to a computer.

Figure 10-2. A print device connected to a computer.

If at all possible, connecting the print devices to server computers is preferable to workstation connections unless the servers are in a location that would be inconvenient for users having to retrieve their printed documents. For example, if you plan to locate your servers in a locked data center or server closet, it would not be practical to locate your print devices there as well.

The best solution, by far, is to connect your print devices directly to the network. This solution enables you to locate your print devices anywhere a network connection is available. You can also designate any computer on the network as a print server, which enables you to use your server computers for their intended purpose, no matter where they are located, as shown in Figure 3.

A print device connected to the network with a single print server.

Figure 3. A print device connected to the network with a single print server.

It is also possible for each computer to function as its own print server, sending jobs directly to the print device, as shown in Figure 4. The only drawback to network–attached print devices is that units with network adapters tend to be more expensive than those without them.

A print device connected to the network, with each computer acting as its own print server.

Figure 4. A print device connected to the network, with each computer acting as its own print server.

Selecting a Print Server

The first deciding factor in selecting a computer to function as a print server is the type of print device connections you plan to use. As mentioned earlier, if you connect a print device directly to a computer, that computer must function as the print server. Network-attached printers provide greater flexibility.

In addition to the type of connections you plan to use, however, you should also base your selection of a print server on the following factors:

  • Print volume The more printing your users do, the greater the burden on the print server. Large numbers of documents use more print server resources than small numbers, lengthy documents use more resources than brief ones, and graphical documents use more than plain text.

  • Print rendering When a print server is running Windows Server 2008 R2 or Windows 7, you can specify whether the client or the print server should render the print jobs. Client-side rendering (CSR) reduces the burden on the print server.

  • Computer resources Print volume and CSR both affect the resources used by print server functions. For example, a workstation with the minimum recommended system requirements can function adequately as a print server, but its functionality as a workstation might be compromised.

Controlling Access to Print Devices

In many cases, administrators grant users unrestricted access to the print devices on the network. However, you might want to regulate access to color print devices, or other units with expensive consumables such as letterhead paper. Windows printers have their own permission system, which functions similar to NTFS and share permissions. You can specify which users can send jobs to a printer and also control access based on other factors, such as the time of day and the user’s priority.

Tip

Print devices are some of the few network hardware components that require maintenance on almost a daily basis. Part of your printing solution should include a decision as to who is responsible for the print devices’ regular maintenance, including tasks such as loading media, clearing paper jams, and replacing toner or ink cartridges. These are thankless tasks that many people try to avoid, so it is important to delegate them decisively. Otherwise, you might find a huge backlog of print jobs left in the queue because the print device is out of paper or toner, and no one has bothered to replenish them.

Other -----------------
- Windows Home Server 2011 : Getting More Out of Control Panel (part 2) - Alternative Methods for Opening Control Panel Icons
- Windows Home Server 2011 : Getting More Out of Control Panel (part 1) - Understanding Control Panel Files
- Windows Home Server 2011 : Using the Local Group Policy Editor (part 3) - Increasing the Size of the Recent Documents List, Enabling the Shutdown Event Tracker
- Windows Home Server 2011 : Using the Local Group Policy Editor (part 2) - Customizing the Places Bar
- Windows Home Server 2011 : Using the Local Group Policy Editor (part 1) - Working with Group Policies, Customizing the Windows Security Screen
- Windows Server 2012 : Backup and Recovery (part 8) - Backing up and restoring Active Directory
- Windows Server 2012 : Backup and Recovery (part 7) - Backing up and recovering your data - Recovering data stored on another server, Recovering the system state
- Windows Server 2012 : Backup and Recovery (part 6) - Backing up and recovering your data - Tracking scheduled and manual backups, Recovering your data
- Windows Server 2012 : Backup and Recovery (part 5) - Backing up and recovering your data - Performing a one-time backup
- Windows Server 2012 : Backup and Recovery (part 4) - Backing up and recovering your data - Scheduling backups
- Windows Server 2012 : Backup and Recovery (part 3) - Backing up and recovering your data - Using the backup utility, Backing up your data
- Windows Server 2012 : Backup and Recovery (part 2) - Developing backup strategies
- Windows Server 2012 : Backup and Recovery (part 1) - Disaster-planning strategies, Disaster preparedness procedures
- Installing Windows Server 2012 and Server Core : Managing and Configuring a Server Core Installation
- Installing Windows Server 2012 and Server Core : Understanding Server Core Installation
- Windows Server 2008 : Using dnscmd - Adding DNS Zones, Creating and Deleting DNS Records
- Windows Server 2008 : Using dnscmd - Clearing the DNS Cache, Working with DNS Partitions
- Windows Server 2008 : Using dnscmd - Retrieving DNS Information, Exporting DNS Data, Forcing Zone Transfers
- Windows Small Business Server 2011 : Deploying SQL Server 2008 R2 for Small Business
- Windows Small Business Server 2011 : Deploying a Second Domain Controller
 
 
 
Top 10
 
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
- First look: Apple Watch

- 3 Tips for Maintaining Your Cell Phone Battery (part 1)

- 3 Tips for Maintaining Your Cell Phone Battery (part 2)
programming4us programming4us